DISCOVERY TRIAGE SAMPLE CASE
Larkspur Construction Group v. Tallowmere Steel Supply, Inc.

EVERYTHING IN THIS FOLDER IS FICTIONAL.
All people, companies, projects, dates, dollar amounts and events were invented for this
sample. Email addresses use reserved example domains (example.com, example.net and
example.org), and phone numbers use the 555-01xx range. Any resemblance to a real person,
company or dispute is a coincidence. Nothing here is legal advice, and none of it is real
evidence.

WHAT THIS IS
A small commercial dispute you can review end to end in about 20 minutes. A general contractor
(Larkspur) bought structural steel for a hospital pavilion from a steel supplier (Tallowmere).
Deliveries came late, and one batch of beams (heat lot 44821) failed inspection. Larkspur is
suing for the cost of the delay and the replacement steel. You are on Larkspur's side and are
reviewing its documents.

The case has 116 documents once everything is opened up, plus 7 from the text
messages (123 in all). The sample case is free and does not count toward the free plan
of Discovery Triage (50 of your own documents on this Mac, every feature included), so you do not
need to buy anything to try it.

WHAT IS IN THE "Documents" FOLDER
  Email           57 messages as .eml files, in one folder per mailbox. 11 of them carry
                  attachments (PDF, Word and Excel), and some are reply or forward threads.
                  Several come from outside counsel and are marked Privileged & Confidential.
                  Plenty are noise: lunch orders, newsletters, HR reminders.
  Site Trailer    one .mbox file (10 messages, 2 attachments)
  Contracts       the supply agreement and a change order (PDF with a text layer)
  Invoices        four invoices (PDF)
  Reports         an inspection report and a mill certificate (PDF)
  Scans           a delivery receipt that is only a picture of a page (no text layer), so it needs OCR
  Photos          a shipping label and a whiteboard photo (PNG, JPEG), also read by OCR
  Memos           Word (.docx) and Rich Text (.rtf) memos and meeting notes
  Legal           a draft notice of breach written by outside counsel (Word)
  Spreadsheets    Excel (.xlsx) and .csv files
  Notes           plain-text notes and logs
  Voicemail       one short audio file (the app reads audio metadata only, it does not transcribe)
  Archives        a .zip with 5 site records inside (the app opens it for you)
  Other Projects, Admin   unrelated papers on purpose, so there is something to mark Not Responsive

TEXT MESSAGES
When you choose "Try the Sample Case" in the app, the texts are imported for you. They come from the
site superintendent's phone: 6 days of conversations with the project manager, with a
crane subcontractor (a group conversation) and with the company's lawyer, plus one photo. They
sit in "Text messages/sms-backup.xml", next to the "Documents" folder. The day with the lawyer is
held for privilege review, as mail to the lawyers is. To try the importer yourself, choose File >
Import Documents... on "Text messages/sms-backup.xml" and choose which conversations to import.

A few files appear twice in different folders. They are exact copies, so you can see
duplicates found by their file hashes (MD5 and SHA-256).

WALKTHROUGH
1. Create a project. Choose File > New Project... (Shift-Command-N) and name it "Sample Case".
   Case Details open next. Click "Load Case Details from File...", choose "Case details.json"
   (it sits next to this file), and click Save. That fills in what the case is about, what to
   look for, the dates, the key people, and Larkspur's lawyers and their email domain, so mail
   to and from the lawyers is held for privilege review as it comes in. "Case details.txt"
   shows the same information in plain words if you would rather type it in yourself. You can
   change them later with Case Details in the toolbar (or Project > Case Details...,
   Shift-Command-D).
2. Import. Click Import in the toolbar (or File > Import Documents..., Command-I) and pick the
   "Documents" folder from this download. Confirm the count shown before the import starts.
   The app copies the files into the project, computes hashes, extracts text, builds the
   search index, and opens the email attachments and the zip. When it finishes you should see
   about 116 documents. The scanned receipt and the photos are read by OCR in the
   background right after, so give them a minute before you search for their words.
3. Search. Try these:
     heat lot 44821        (the defective beams: emails, reports, notes and OCR'd images)
     "liquidated damages"  (the contract, the owner's notice and internal emails)
     ultrasonic            (the inspection report and the supplier's own test log)
     "under protest"       (found only after OCR: it is in the scanned receipt)
   Click a hit to read the document and see the matches highlighted. Look at an email with
   attachments: the attachments sit with it as a family.
4. Review and code. In Review Mode (Shift-Command-R) press 1 for Responsive, 2 for Not
   Responsive, 3 for Needs Review and P for Privileged, then use the arrow keys to move on.
   Good ones to try: "Between us" from Garrett Voss (responsive, a key admission),
   "Lunch order Wednesday" (not responsive), and the messages from Marguerite Okoro at
   Pellham Okoro LLP (privileged). Tags sit under the document with the coding buttons: click
   one to add it, or make a new one there. To tag several documents at once, select them in
   the list and use Tag.
5. AI review (optional). This needs a Mac with Apple Intelligence turned on. Everything else in
   this walkthrough works without it. Click AI Review in the toolbar. Step 1 shows your Case
   Details. In step 2 choose what to review (for example all documents). In step 3 keep
   "Find responsive documents" and "Find privileged documents" ticked and click Run.
   Results are grouped: Possibly privileged first, then Likely responsive and Likely not
   responsive. Each row gives a one-sentence reason and a High, Medium or Low confidence;
   click a row to open the document, and click AI Review again to come back to the results.
   Emails to or from Pellham Okoro LLP are flagged as possibly privileged by a simple rule
   (their lawyers and email domain from the Case Details), not by the AI. The AI only
   suggests. You decide, and documents flagged as possibly privileged are held back from
   production until you answer.
6. Privilege log. Once you have coded some documents as privileged, click Productions in the
   toolbar (or Production > Productions..., Shift-Command-E) and use Export Privilege Log.
7. Produce. In the Productions window click Create Production. Set the Bates prefix to SAMPLE,
   keep the default start number, and create it. Review the pre-production summary, which
   shows what will and will not be produced. Then use Export... to write the Concordance load
   file, the Opticon file, the native files, text and Bates-stamped PDF images to a folder of
   your choice.
8. Optional extras: View > Audit Log... (Option-Command-L) lists every coding decision and
   production, and File > Back Up Project... (Option-Command-B) makes a backup.

THINGS TO NOTICE
  * Two "hot" documents are in the case. Garrett Voss's email "Between us" and the supplier's
    own test log both show that Tallowmere knew heat lot 44821 had failed.
  * The case is not one-sided. Internal Larkspur emails admit that formal notice was late.
  * Raul Esteban forwards a lawyer's advice to an outside engineer. Is privilege waived? The
    app leaves that call to you.
  * One email to the lawyer (Call Thursday?) is only about scheduling. Is that privileged?
  * Outlook files: Discovery Triage also reads PST, OST and MSG files. This sample uses
    standard email (.eml and .mbox) so that it can be built without Outlook.

PRIVACY
Discovery Triage works on your Mac only. Nothing in this sample is uploaded anywhere, and the
files here are not real data.

Questions: support@discoverytriage.com    More: https://discoverytriage.com
